Device redirection for remote systems

ABSTRACT

The present disclosure provides systems and method for redirecting control of a client side connected USB device from the client to the server in a remote system. Specifically, the present disclosure creates a simulated USB device at the server. The simulated USB device is treated as a proxy for a redirected USB device at the client. The client side redirected USB device is not treated as the USB device but, rather, acts as a pass through to facilitate communication between requesting applications and the client connected device. The simulated USB device allows an application to send requests for a local device to the simulated USB device at the server. The simulated USB device then processes the requests and forwards the requests to the local device connected to the client.

BACKGROUND

Remote systems, such as Terminal Service™ (TS) systems and VirtualDesktop Infrastructure (VDI) systems provided by the MicrosoftCorporation, involve a server computer system (sometimes referred to asa remote server) where clients, acting locally, use remote applicationprograms hosted by and/or resident on such a server system. In theseremote systems, client computers rely on the remote server computer toprovide computing functionality through the resident applicationprograms. Examples of remote application programs include wordprocessing, multimedia, and data management programs, among others.

Benefits of remote systems are that the client computers can berelatively low-powered since most functionality and computation has beenmoved to or otherwise takes place at the remote server. Anotheradvantage is that data can reside at the physical location of the remoteserver and can be acted upon at that location by remote applicationprograms without having to be transferred over relatively slowcommunications links to the client computers. When client-side requestsare forwarded to the server for action, the requests are said to beredirected to the server.

Given the benefits of moving functionality to the remote server, manyapplications have been developed to work remotely. However, someapplications are designed to operate solely on the local level, e.g.,device drivers for Universal Serial Bus (USB) devices. Meanwhile, manyother remote applications operate in conjunction with these localizeddrivers to interface with or otherwise control the actual USB devices.Since existing server-side applications are unable to directlycommunicate with a client side USB device, e.g., access the low-levelinterface of the device itself, the USB device drivers must be installedon the local client system where the USB device is physically connected.A server-side application attempting to communicate with the USB devicedoes so by interfacing with the USB device driver installed on theclient through what is known as “high-level redirection.” Aspects ofhigh-level redirection are described in more detail in co-pending patentapplication titled “Plug and Play Device Redirection for RemoteSystems,” U.S. application Ser. No. 11/278,529, which is incorporatedherein by reference. High-level redirection, which operates onhigh-level interfaces, however, prevents the installation of specific,locally designed applications on remote servers. That is, these locallydesigned applications or drivers need to access the low-level interfacesof the USB devices and high-level redirection does not enable thisfunctionality.

Consequently, to enable USB device functionality or use by a remoteserver, one solution has been to connect the USB device to the remoteserver itself. Connecting the device to the remote server is notpractical in an enterprise environment where the server may not bereadily found or accessed. As stated before, the other option is toinstall the USB device driver on the client and interface with the USBdevice through a set of high-level, specifically created, applications.This solution is also impractical for the many classes of USB devices inwhich no high-level redirection application has been created. Moreover,such a solution requires significant installations on the clientcomputer system such that replacing the client computer system is moreproblematic once the installations have occurred.

SUMMARY

The present disclosure describes systems and methods that use and/orenable the redirection of control of a USB device connected locally to aclient computer system from the client to a remote server computersystem, both of which are part of a remote system. More specifically,the present disclosure describes the creation of a simulated USB deviceat the remote server. The simulated USB device is treated as a proxy fora USB device connected to the client system. The client-side USB deviceis not treated as the USB device but, rather, acts as a pass through tofacilitate communication between a requesting server side applicationand the device connected locally to the client. The simulated USB deviceallows a server side application to send requests for a local device tothe simulated USB device at the server. The simulated USB device thenprocesses the requests and forwards the requests to the device connectedlocally to the client.

Embodiments of the present disclosure describe methods for creating thesimulated USB device at the server in a remote system. When a device isconnected locally to the client, it is determined whether control of thedevice should be redirected to the server. Upon determination thatcontrol should be redirected, the specific identifier associated withthe device is transformed into a globally unique identifier. Theglobally unique identifier conveys to the system that a generic USBdevice driver should be installed at the client. The generic USB devicedriver transmits device parameters for configuring a simulated USBdevice from an instance of the redirected USB device at the client toserver side application. The device parameters are received at theserver and used to create a simulated USB device at the server.

In other embodiments of the present disclosure, methods are describedfor redirecting isochronous requests to and from the simulated USBdevice at the server. Specifically, a first request and second requestare received for forwarding to the simulated USB device. The firstrequest is sent to the simulated USB device. Feedback is received fromthe simulated USB device that the request has been processed, eventhough the request has not been processed yet. Upon receipt of thefeedback, the second request is sent to the simulated USB device. Thefirst request and second request forwarded to the application at theclient.

In another embodiment, a remote system for redirecting requests for adevice connected locally to a client to a simulated USB device at aserver is described. The system includes communicatively connectedclient and server computers, wherein the client computer is connectedlocally to a device. The system further includes a redirected USB deviceat the client that is not treated as the actual USB device. The systemfurther includes a generic USB driver at the client that is configuredto communicate with the instance of the local USB device and anapplication. The system further includes a simulated USB device at theserver that is treated as the actual USB device and receives requestsfor the device from the application.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE CONTENTS

The detailed description is described with reference to the accompanyingfigures.

FIG. 1 illustrates an exemplary computing environment.

FIG. 2 is an illustration of a remote system that includes a servercomputer and client computer.

FIG. 3A is an illustration of a remote system for redirecting control ofa local device from a client computer to a server computer.

FIG. 3B is an illustration of an alternative embodiment from that shownin FIG. 3B showing the use of a filter driver.

FIG. 4 is a flow diagram illustrating an exemplary method for creating asimulated USB device at a server computer.

FIG. 5 is a flow diagram illustrating an exemplary method forredirecting communication to and from a simulated USB device located ata server computer.

DETAILED DESCRIPTION

Referring now to the drawings, in which like numerals represent likeelements, various embodiments will be described. In particular, FIG. 1and the corresponding discussion are intended to provide a brief,general description of a suitable computing environment in whichembodiments may be implemented.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Other computer systemconfigurations may also be used, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and the like.Distributed computing environments may also be used where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote memory storage devices.

Referring now to FIG. 1, an exemplary computer architecture 100 for acomputer system 102 utilized in various embodiments will be described.The computer architecture 100 shown in FIG. 1 may be configured in manydifferent ways. For example, the computer 102 may be configured for usein a remote system as a server or a client. As shown, computer 102includes a central processing unit 105 (“CPU”), a system memory 106,including a random access memory 108 (“RAM”) and a read-only memory(“ROM”) 110, and a system bus 112 that couples the memory 106 to the CPU104. A basic input/output system containing the basic routines that helpto transfer information between elements within the computer, such asduring startup, is stored in the ROM 108. The computer 102 furtherincludes a mass storage device 114 for storing an operating system 116,application programs 118, and other program modules.

The mass storage device 114 is connected to the CPU 104 through a massstorage controller (not shown) connected to the bus 112. The massstorage device 114 and its associated computer-readable media providenon-volatile storage for the computer system 102. Although thedescription of computer-readable media contained herein refers to a massstorage device, such as a hard disk or CD-ROM drive, thecomputer-readable media can be any available media that can be accessedby the computer system 102.

By way of example, and not limitation, computer-readable media maycomprise computer storage media and communication media. Computerstorage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solidstate memory technology, CD-ROM, digital versatile disks (“DVD”), orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer system 102.

According to various embodiments, the computer system 102 operates in anetworked environment using logical connections to remote computersthrough a network 120, such as the Internet. Remote computers mayinclude one or more computer systems 150 and 160 comprising eitherclients or remote servers. The computer system 102 may connect to thenetwork 120 through a network interface unit 122 connected to the bus112. The network interface unit 122 may also be utilized to connect aclient and server in a remote system. The network 120 may be implementedin a number of ways to support such networking contexts, including bothwired-based technologies and wireless technologies. Aspects of thisinvention are not limited to one specific network architecture ornetwork technology. The computing environment 100 is representative ofdifferent architectures which include direct dialup via modem,enterprise LANs (local area networks), WANs (wide area networks) and theInternet. Network 120 connects the server computer 202 to one or moreclient computers (e.g., client computer 204). Furthermore, the network120 connection between the server computer and client computer mayimplement a transport protocol such as transmission control protocolover Internet protocol (TCP/IP).

The computer system 102 may also include an input/output controller 124for receiving and processing input from a number of devices, such as: akeyboard, mouse, electronic stylus and the like 126. Similarly, theinput/output controller 124 may provide output to a display screen, aprinter, or some other type of device 126.

As mentioned briefly above, a number of program modules and data filesmay be stored in the mass storage device 114 and RAM 108 of the computersystem 102, including an operating system 116 suitable for controllingthe operation of a networked computer, such as: the WINDOWS 7®, WINDOWSSERVER®, WINDOWS SHAREPOINT SERVER®, operating systems from MICROSOFTCORPORATION; UNIX; LINUX and the like. The mass storage device 114 andRAM 108 may also store one or more program modules.

A remote system 200 incorporating aspects of the present disclosure isshown in FIG. 2. The remote system 200 includes one or more computersthat utilize the computer environment 100 as described above inconjunction with FIG. 1. Specifically, the remote system 200 includes aserver computer 202 and one or more client computers 204 over network210. Client computer 204 includes generic device driver 212 and servercomputer 202 includes a USB device driver 205 and a simulated USB device206 to facilitate redirecting control of device 208 locally connected tothe client computer 204 to the server 202.

In this example, one client computer 204 is depicted however, in otherimplementations, the remote system 200 may include multiple clientcomputers. Client computer 204 depicts a client computer to which one ormore local devices 208 are connected. Local devices 208 are the physicalUSB devices connected to client computer 204. Access and control oflocal USB devices 208 connected at the client computer 204 may beredirected to the server computer 202 such that the local devices 208are selectively accessed and controlled by the server computer 202. Theremote system 200 may be a Terminal Service™ system, in one embodiment,or in another embodiment, system 200 may be a Virtual DesktopInfrastructure system as provided or defined by the MicrosoftCorporation, where multiple client computers (e.g., client computer 204)rely on server computer 202 for all or certain application programs thatprovide functionality. Other remote systems may also implement aspectsof the present disclosure as will be apparent to those skilled in theart.

The server computer(s) 202 may implement a communication protocol suchas remote data protocol (RDP) defined by the Microsoft Corporation, inorder to pass data or information or otherwise communicate with oneanother. The use of such communication protocols, and particularly RDP,may be implemented in the context of a remote system such as a TerminalServices™ system or the Virtual Desktop Infrastructure.

Client computer 204 is equipped with one or more device ports thatconnect USB devices, such as local devices 208. The device ports includeUSB 1.0, 1.1 and 2.0, and FireWire (IEEE 1394) ports that supportexisting and future standards. In particular, the device ports allow theconnection of the local devices 208 to client computer 204. Localdevices 208 include, but are not limited to, digital cameras, videocameras, hard disk storage devices, digital media recorders, printers,scanners, etc. As described in detail below, client computer includes ageneric device driver 212 that redirects I/O responses from local device208 to USB device driver 205 and simulated USB device 206 at the server202.

Server computer 202 includes a simulated USB device 206 and USB devicedriver 205. In particular, as discussed in detail below, an applicationis configured to intercept all I/O requests to a simulated USB device206 and forward the requests to local USB device 208. The simulated USBdevice 206 is created at the server computer 202 and functions as theUSB device for the local device 208. Once the simulated USB device iscreated, the remote system 200 installs the necessary USB device driver205 for the local device 208 at the server computer 202. An actualdevice driver for the local device 208 is not created at the clientcomputer 204. The application cannot differentiate the simulated USBdevice 206 from redirected USB device 208 and communicates withsimulated USB device 206 as a proxy for the instance of local USB deviceat the client.

Communications to server computer 202 and client computer 204 overnetwork 210 may make use of I/O USB request packets (URB) communicatedover RDP. In particular, application programs resident at the servercomputer 202 may implement URB to communicate with local devices 208.The URB may be communication data originating from application programsthat includes requests to one or more of local devices 208. As will bedescribed in more detail below, the I/O requests may be transmittedusing isochronous requests in an optimized manner.

FIG. 3A is an illustration of a remote system 300, which, in someembodiments, represents a more detailed view of remote system 200, shownand described in conjunction with FIG. 2. Remote system 300 involvesredirecting control of a local device 208 from client system 316 toremote server system 318.

Remote system 300 is configured such that communication betweenapplication 360 and the instance of local USB device 306 is redirectedvia Simulated USB Device 312 and client side application 310. In oneembodiment applications 310 and 360 are remote service clientapplications, running client side and server side respectively. Theremote service client applications 310 and 360 may be a remote processsuch as a process implemented by Terminal Services™ or the VirtualDesktop Infrastructure. The remote service client application 310 mayalso be configured as a driver or other software configured to route I/Orequests. Application 310 may primarily be used to provide communicationbetween client system 316 and remote server system 318. In oneembodiment, application 310 establishes communication between a clientsystem 316 and remote server system 318 by creating a virtual channel totransfer USB request packets between a terminal server and a terminalclient.

As discussed above, in a typical remote system, an instance of a USBdevice is created at the client computer to which the USB device isconnected. As the instance of the USB device is created at the client,the remote system installs the USB device driver necessary for the USBdevice at the client computer as well. I/O requests from clientcomputers in the remote system cannot be processed at remote serversystem because neither the USB device driver nor the instance of the USBdevice exists at the remote server system. I/O requests must, therefore,be directed to the client where the USB device driver and instance ofthe USB device exist.

The present disclosure relates to a remote system 300 that enablesdirect communication between the application 360 and a simulated USBdevice 312 located at the remote server system 318.

Local device 208 (not depicted) is connected to the client system 316 atthe USB hub driver 302. The USB hub driver 302 may be in communicationwith one or more USB ports. Local device 208 may be inserted into one ofthe USB ports. Once local device 208 is inserted into a USB port, thelocal device 208 is communicatively connected to client system 316 viaUSB hub driver 302. It will be appreciated that multiple local devices208 may be connected via the USB hub driver 302 at one time.

USB hub driver 302 discovers the one or more local devices 208 insertedinto the USB ports. USB hub driver 302 determines if any of the localdevices 208 should be configured for redirection to remote system 318.In one embodiment, upon this determination, USB hub driver 302 providesa list of one or more local devices 208 that could be redirected to auser of client system 316. The USB hub driver 302 then receives aselection of one or more local devices 208 for redirection. In anotherembodiment, USB hub driver 302 automatically redirects control of alocal device 208 upon determining that control of the local device 208should be redirected to the remote server system 318.

When a local device 208 is selected for redirection, the USB hub driver302 exposes an interface to redirect control of the local device 208 tothe remote server system 318. In order to redirect control of localdevice 208 to remote server system 318, USB hub driver 302 performsdevice morphing on the local device 208. Device morphing occurs when anidentifier associated with a local device 208 is transformed from aunique identifier for the local device 208 to a globally uniqueidentifier (GUID) common to the interface exposed by the USB hub driver302. The identifier is preconfigured and indicates to the system thatgeneric device driver 308 needs to be installed for the device. Theglobally unique identifier may be a randomly generated value when remotesystem 300 is configured. Once the remote system is configured, theidentifier stays the same. The globally unique identifier is stored atthe USB hub driver 302.

USB hub driver 302 uses the globally unique identifier to create aninstance of local USB device 306 at client system 316. The remote system300, however, does not recognize the instance of local USB device 306 asthe actual device. Rather, the instance of the local USB device 306 actsas a pass through to facilitate communication with local device 208.

When local device 208 is identified with a globally unique identifier,the system determines the software necessary to install generic devicedriver 308 and installs generic device driver 308 at client system 316.When generic device driver 308 is installed at the client system 316, aUSB device driver for the specific local device 208 is not installed atthe client system. Rather, generic device driver 308 exposes aninterface to communicate with both the instance of local USB device 306and application 310.

Generic device driver 308 serves as a gateway between client system 316and remote server system 318. I/O requests from remote server system 318to client system 316 are repackaged and routed through generic devicedriver 308 and vice versa. Generic device driver 308 is configured tointerpret for the local device 208 what application 310 is asking of itand to interpret for the application 310 the response from local device208.

Generic device driver 308 assists in the creation of USB device driver314 and simulated USB device 312 at remote server system 316.Specifically, generic device driver 308 receives device parameters fromthe instance of the local USB device 306. Device parameters includeparameters necessary to configure simulated USB device 312 at remoteserver system 316. The generic device driver 308 forwards the deviceparameters to application 310. Application 310 communicates the deviceparameters to application 360 at remote server system 316. The deviceparameters are used by application 360 at remote server system 318 toconfigure simulated USB device 312. In one embodiment, the deviceparameters are sent from the generic device driver 308 in an Add Devicemessage.

Simulated USB device 312 is installed at remote server system 318 usingthe device parameters sent over the network. The device parameters areused to configure the simulated USB device 312 so that it is identicalto the instance of the local USB device 306 at client system 316. Inother words, application 360 is unable to differentiate betweensimulated USB device 312 and the instance of local USB device 306 atclient system 316 and interacts with simulated USB device 312 as if itwere the instance of local USB device 306. Once the simulated USB device312 is created, the applications 310 and 360 can communicate with itdirectly. The system recognizes simulated USB device 312 as the actualUSB device and installs the necessary driver, represented as USB devicedriver 314. The USB device driver 314 is the actual driver for the localUSB device 306. In one embodiment, both USB device driver 314 andsimulated USB device 312 are stored at the remote server system 318 andpersist in storage even after the local device 208 has been disconnectedfrom client system 316. In another embodiment, the simulated USB device312 may be removed when local device 208 is disconnected from the clientsystem.

Simulated USB device 312 receives I/O requests for local device 208routed through application 310. Simulated USB device 312 then repackagesthe I/O requests for forwarding to application 310. Communicationprotocols such as RDP compress I/O requests before transmission over anetwork. Simulated USB device 312 is configured to repackage I/Orequests before they are compressed by such a communication protocol.Sending repackaged I/O requests eliminates transmission of unnecessarydata and condenses the request into the smallest number of bytes withoutlosing information. The simulated USB device 312, thus, determines whichinformation is useful and repackages the I/O requests to contain onlythe data necessary for the local device to perform an action. Once anI/O request is repackaged by simulated USB driver 312, it is compressedusing a communication protocol, such as RDP, and transmitted over thenetwork as a USB request packet. Application 310 receiving the requestthen decompresses the USB request packet and adds any informationnecessary for local device 208 to understand the I/O request. In anotherembodiment, generic device driver 308 decompresses the USB requestpacket and adds any information necessary for local device 208 tounderstand the I/O request.

In a similar manner, I/O responses from local device 208 to simulatedUSB device 312 are repackaged at either application 310 or genericdevice driver 308. The repackaged I/O response is then compressed into aUSB request using a communication protocol such as RDP. The USB requestis transmitted over the network from application 310 to simulated USBdevice 312. Upon receipt of the USB request, the simulated USB device312 decompresses the USB request and adds any information necessary forthe USB device driver 314 to understand the I/O response.

In an embodiment, URB write requests are sent between server sideapplication 360 and client side application 310 in an optimizedisochronous manner. In general, isochronous requests include a time whenthe request should be processed by the device. Once the URB packet isprocessed by the device, feedback is sent to indicate that a next URBpacket should be sent. Isochronous requests generally ensure that URBpackets are not received out of order nor are URB packets lost duringtransmission. However, in a lossy and high latency network, isochronousrequests can cause unnecessary delay between receipts of URBs. The delayfrom network latency may also increase due to the delay caused by thefeedback mechanism. In an embodiment, the present disclosure decreasesthe delay caused by optimizing isochronous requests by “faking”feedback.

Specifically, when receiving I/O requests sent from application 360,simulated USB device 312 sends feedback requesting that a second URB besent before the first URB is even forwarded to application 310.Alternatively, when sending I/O requests to application 310, application360 receives “faked” feedback allowing application 360 to send a secondURB before the first URB has been received. This feedback mechanismoffsets the increased network latency experienced in systems that useisochronous data requests.

In another embodiment, the instance of local USB device 306 and thegeneric device driver 308 only exist for the duration that local device208 is connected to the client system 316. If local device 208 isdisconnected and then reconnected, the instance of the local USB device306 and generic device driver 308 must be recreated using the storedglobally unique identifier for local device 208.

FIG. 3B depicts another embodiment of a remote system 300 where controlof a local device 208 is redirected from client system 316 to remotesystem 318.

In FIG. 3B device morphing occurs outside of the USB hub driver 302 atthe local USB device filter driver 304. The local USB device filterdriver 304 transforms the specific identifier associated with localdevice 208 into a globally unique identifier. The globally uniqueidentifier is stored at the local USB device filter driver 304 inassociation with local device 208.

FIG. 4. is a flow diagram illustrating an exemplary method 400 forcreating a simulated USB device at a server computer. Some operationsare optional, and these optional operations are encompassed by dashedlines.

At operation 402, a local device is discovered as connected to a USBport. In one embodiment, the local device is discovered by USB hubdriver. Flow then proceeds to either operation 404 or operation 408.

At operation 404, an embodiment provides a device selection screen. Thedevice selection screen may be a user interface with one or moreelements for selection. The USB hub driver recognizes local devices thatare inserted into the one or more USB ports. In one embodiment, the USBhub driver determines which local devices should be provided in thedevice selection screen. For example, three local devices may beconnected to the client system via the USB ports. The first local deviceis a keyboard device, the second local device is a printer device, andthe third local device is a speaker device. The USB hub driver maydetermine that the user should not redirect the keyboard as control ofthe keyboard should be maintained locally at the client computer. On theother hand, the USB hub driver may determine that the user couldredirect the printer device or the speaker device as control of theselocal devices could be maintained remotely at the server computer. Aftermaking this determination, the USB hub driver provides to the clientsystem only the printer device and the speaker device as selectabledevices in a device selection screen. Flow then proceeds to operation406.

At operation 406, a selection of a local device for redirection isreceived. The selection is made when a user selects a local device fromthe device selection screen. Using the example described with referenceto operation 404, a user may be presented with a printer device and aspeaker device as selectable devices in a device selection screen. Inthis example, the user may select the printer device for redirection andnot select the speaker device. As will be appreciated by one skilled inthe art, none, one, or more than one local device may be selected fromthe device selection screen for redirection. If a local device is notselected for redirection, the unselected local device retains itsspecific identifier and the USB device driver for the unselected localdevice is installed at the client system. Consequently, control of theunselected local device is not redirected to the remote server system.Alternatively, if a local device is selected for redirection, flowproceeds to operation 408.

At operation 408, the identifier for the local device is changed from anidentifier specific to the local device to a globally unique identifier.In one embodiment, this transformation occurs at the USB hub driver. Inanother embodiment, this transformation occurs at the local USB devicefilter driver. Flow then proceeds to operation 410.

At operation 410, an instance of the redirected USB device is created.In one embodiment, the instance of the redirected USB device is createdat client system by USB hub driver. In another embodiment, the instanceof the redirected USB device is created by the local USB device filterdriver that morphed the local device identifier. The remote system doesnot recognize redirected USB device as the actual USB device. Rather,redirected USB device acts as a pass through and facilitatescommunication with local device. Flow then proceeds to operation 412.

At operation 412, generic device driver is created. Local systemrecognizes that local device has been associated with a globally uniqueidentifier. This recognition triggers the local system to installgeneric device driver at the client system. When generic device driveris installed at the client system, a USB device driver for the localdevice is not installed at the client. Generic device driver exposes aninterface for communication with application. This interface allowsgeneric device driver to forward information from local device tosimulated USB device via client side and server side applications. Theinterface also allows generic device driver to receive informationforwarded from simulated USB device via application for forwarding tolocal device. Flow then proceeds to operation 414.

At operation 414, device parameters for local device are communicatedfrom client side application to server side application. Deviceparameters may include software necessary to configure simulated USBdevice. In one embodiment, the device parameters are sent in an AddDevice message. As discussed above, the device parameters may berepackaged such that only those device parameters necessary to configuresimulated USB device are transmitted. Once the device parameters arerepackaged, the request is compressed using a communication protocolsuch as RDP. The compressed and repackaged device parameters are sentover the network to create simulated USB device 312 at the remote serversystem. Flow then proceeds to operation 416.

At operation 416, the simulated USB device for local device is createdat the remote server system using the device parameters. Upon creationof the simulated USB device, the remote system recognizes it as theactual USB device and installs the necessary USB device driver. Asdiscussed above, USB device driver is the actual driver for localdevice. Once simulated USB device is created and USB device driver isinstalled, I/O requests for local device are sent to simulated USBdevice from server side applications. Simulated USB device then forwardsthe I/O requests to local device via client side applications.

FIG. 5 is a flow diagram illustrating an exemplary method 500 forredirecting communication to and from a simulated USB device 312 locatedat a server computer 202.

At operation 502, a first request is received to communicate with alocal device. The first request may be an isochronous I/O write requestreceived by a server side application 360 and includes an indication ofa first processing time. Some exemplary requests include requests fordata from the device and submission of data to the device. As will beappreciated by one skilled in the art, any number of requests iscontemplated within the scope of the present disclosure. For example, alocal device may be a USB connected speaker playing a song. As speakersdo not usually have storage, the server side application 360 mustcontinuously send segments of the song for the speaker to play. Therequest is routed to simulated USB device 312. Once the simulated USBdevice 312 receives the first request, flow proceeds to operation 504.

At operation 504, the simulated USB device 312 repackages the I/Orequest. As discussed above, the simulated USB device 312 removesunnecessary data from the I/O request. Removing unnecessary datacondenses the I/O request into the smallest number of bytes withoutlosing information. The repackaged request is then compressed using acommunication protocol such as RDP. Flow then proceeds to operation 506.

At operation 506, “fake” isochronous feedback is received at the serverside application 360. As discussed above, in a system that employsisochronous data requests, a next USB request may not be sent before thefirst USB request is processed at the time indicated in the firstrequest itself. As a result, delays in a high latency network areincreased from the additional delay caused by the feedback mechanism. Tooffset the increased delay, simulated USB device 312 sends “fake”isochronous feedback to server side application 360 indicating that thefirst request has been completed by local device. In reference to theexample in operation 502, server side application 360 may receive “fake”feedback that a previous segment of music had already been transmittedby the local device. Server side application 360 will, then, consider ittimely to send a request for a next segment of music. Flow then proceedsto operation 508.

At operation 508 a second request for a next segment of music is sentfrom server side application 360 to simulated USB device 312. Like thefirst request, the second request includes an indication of a secondprocessing time. As discussed above, simulated USB device acts as theactual device and processes the received request. Simulated USB device312 compresses the I/O request and adds information necessary for USBdevice driver 314 to understand the request. Flow then proceeds tooperation 510.

At operation 510, the first request and second requests are received atclient side application from simulated USB device 312. In oneembodiment, client side application decompresses the requests and addsinformation necessary for local device 208 to understand the request. Aswill be appreciated, the first and second requests may not be receivedby client side application at the same time. For simplicity purposes,the first and second requests will be discussed in operation 510 asbeing processed simultaneously. Flow then proceeds to operation 512.

At operation 512, the first request and second are sent to generic USBdriver to be forwarded to local device. If client side application hasdecompressed and added necessary information to the first and secondrequests, the requests are processed as is by generic device driver forforwarding to local device. Processing comprises the generic devicedriver determining what application is requesting of local device andcreating a local device 208 understandable requests. If client sideapplication did not decompress or add information to the first andsecond requests, the generic device driver decompresses and addsinformation to the requests before processing the requests forforwarding to local device. Flow then proceeds to operation 514.

At operation 514, the first request is transmitted to local device atthe first processing time. As discussed above, the first processing timeis included in the request and indicates a time at which the requestshould be processed. Once the first request is processed, flow proceedsto operation 516.

At operation 516, the second request is transmitted to local device atthe second processing time. As discussed above, the second processingtime is included in the request and indicates a time at which therequest should be processed. The second request is then processed. Flowthen terminates.

It will be clear that the systems and methods described herein are welladapted to attain the ends and advantages mentioned as well as thoseinherent therein. Those skilled in the art will recognize that themethods and systems within this specification may be implemented in manymanners and as such is not to be limited by the foregoing exemplifiedembodiments and examples. In other words, functional elements beingperformed by a single or multiple components, in various combinations ofhardware and software, and individual functions can be distributed amongsoftware applications at either the client or server level. In thisregard, any number of the features of the different embodimentsdescribed herein may be combined into one single embodiment andalternative embodiments having fewer than or more than all of thefeatures herein described are possible.

While various embodiments have been described for purposes of thisdisclosure, various changes and modifications may be made which are wellwithin the scope of the present disclosure. Numerous other changes maybe made which will readily suggest themselves to those skilled in theart and which are encompassed in the spirit of the disclosure and asdefined in the appended claims.

What is claimed is:
 1. A computer implemented method for redirectingcontrol of a device connected to a first data processing system to asecond data processing system that is in communication with the firstdata processing system, the method comprising: discovering that thedevice is connected to the first data processing system; determiningthat control of the device should be redirected to the second dataprocessing system assigning a globally unique identifier to the device;subsequent to determining that the device is identified by the globallyunique identifier, installing a device driver at the first dataprocessing system instead of installing an actual device driver for thedevice at the first data processing system; creating an instance of thedevice at the first data processing system; conveying a device parameterFor configuring a simulated device from the device driver to the seconddata processing system, wherein the simulated device is identical to theinstance of the device at the first data processing system and isconfigured to trigger the second data processing system to install anactual device driver at the second data processing system; receiving afirst request and a second request at the device driver from the seconddata processing system, wherein the first request and the second requesteach comprise instructions for the device and the first request isassociated with a first processing time and the second request isassociated with a second processing time and the first processing timeis earlier than the second processing time; sending the first request tothe device at the first processing time; and sending the second requestto the device at the second processing time.
 2. The computer implementedmethod of claim 1, wherein the method further comprises: subsequent todiscovering the device, determining whether the device could beredirected; subsequent to determining that the device could beredirected, providing the device to a user for selection in a deviceselection window.
 3. The computer implemented method of claim 1, whereinthe globally unique identifier is GUID common to an interface.
 4. Thecomputer implemented method of claim 1, wherein the globally uniqueidentifier is assigned at a filter driver outside of a hub driver. 5.The computer implemented method of claim 1, further comprising:subsequent to creating the instance of the device, creating a genericdevice driver.
 6. The computer implemented method of claim 1, furthercomprising: compressing the device parameter using a remote desktopprotocol.
 7. The computer implemented method of claim 1, whereinconveying the device parameter comprises sending the device parameter toan application that communicatively connects the second data processingsystem and the first data processing system.
 8. The computer implementedmethod of claim 7, wherein communicative connectivity is established bycreating a virtual channel.
 9. The computer implemented method of claim1, further comprising: subsequent to receiving the first request,determining, by the device driver, if additional information needs to beincorporated into the first request for the device to understand thefirst request.
 10. The computer implemented method of claim 1, furthercomprising: subsequent to receiving the second request at the devicedriver, determining, by the generic device driver, if additionalinformation needs to be incorporated into the second request for thedevice to understand the second request.
 11. The computer implementedmethod of claim 1 wherein the device is a USB device.
 12. The computerimplemented method of claim 1 wherein the device is a firewire device.13. The computer implemented method of claim 1 wherein the first dataprocessing system is a client computer.
 14. The computer implementedmethod of claim 1 wherein the second data processing system is a servercomputer.
 15. The computer implemented method of claim 1 wherein thedevice driver at the first data processing system is a generic devicedriver.
 16. The computer implemented method of claim 1 furthercomprising simultaneously receiving the first request and the secondrequest at the first data processing system.
 17. The computerimplemented method of claim 1 further comprising transforming anidentifier associated with the device to the globally unique identifierfor the device.
 18. The computer implemented method of claim 17, furthercomprising formatting the first request and the second request as USBrequests.
 19. A computer implemented method of controlling a deviceconnected to a first computer by a second computer, the methodcomprising: identifying that the device has been selected forredirection; receiving one or more device parameters from a genericdevice driver on the first computer, wherein the generic device driveris based on a globally unique identifier for the device; using, whereinthe device parameters are used to create a simulated device on thesecond computer; installing a device-specific driver for the device atthe second computer based on the simulated device; sending a firstrequest and second request for the device to the generic device driveron the first computer, wherein the first request and the second requestcomprise instructions for the device and each of the first request andsecond request is associated with a processing time and the processingtime for the first request is earlier than the processing time of thesecond request; in response to sending the second request, receivingfaked feedback for allowing a third request to be sent to the genericdevice driver on the first computer before the second request isreceived by the first computer.
 20. The computer implemented method ofclaim 19, further comprising compressing the first request receivedusing a remote desktop protocol.
 21. The computer implemented method ofclaim 19 wherein the driver is a USB driver.
 22. The computerimplemented method of claim 19 wherein the first computer is a client.23. The computer implemented method of claim 19 wherein the secondcomputer is a server.
 24. A remote system comprising: a first dataprocessing system; a second data processing system in communication withthe first data processing system; a device connected to the first dataprocessing system, wherein the device is associated with an identifier,and wherein the identifier of the device is transformed into a globallyunique identifier when the device is selected for redirection; aninstance of the device at the first data processing system, wherein theinstance of the device is not treated as an actual device; a genericdriver at the first data processing system, wherein the generic driveris configured to communicate with the instance of the device and a firstapplication at the first data processing system; a simulated device atthe second data processing system, wherein the simulated device isidentical to the instance of the of the device and is treated as theactual device, and wherein the simulated device is configured to use oneor more parameters specific to the device received from the genericdriver and to send a first request to the instance of the device; a realdriver at the second data processing system communicatively coupled tothe simulated device; and a second application at the second dataprocessing system communicatively coupled to the simulated device andthe first application, wherein the second application is configured toreceive feedback from the simulated device that the first request wasprocessed by the device, wherein the feedback is sent from the simulateddevice before the first request is actually processed by the device. 25.The remote system of claim 24, the system further comprising: a hubdriver at the first data processing system, the hub driver configured totransform a specific identifier of the device into a globally uniqueidentifier.
 26. The remote system of claim 24, the system furthercomprising: a filter driver at the first data processing system, thefilter driver configured to transform a specific identifier of thedevice into a globally unique identifier.
 27. The remote system of claim24, wherein the first data processing system communicates with thesecond data processing system using a remote desktop protocol.
 28. Theremote system of claim 24, wherein device is a USB device.
 29. Theremote system of claim 24, wherein first data processing system is aclient system.
 30. The remote system of claim 24, wherein second dataprocessing system is a server system.